Conversation
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
commit: |
🦋 Changeset detectedLatest commit: 88bf924 The changes in this PR will be included in the next version bump. This PR includes no changesetsWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Hey, @techniq. I have a question: When are you planning to merge this PR so we can finally get the Svelte 5 support? 🤗 |
|
Hey @HicaroD, thanks for the kind words 🫶. Sorry, I don't have a rough release date set yet. There are a good number of improvements I would like to include in With that said, you 100% can use it today via I could see pushing some items to Related: I also need to migrate Svelte UX fully over to Svelte 5 (it's Svelte 3-5 compat with Svelte 3/4 state/syntax). Both libraries have already been migrated to Tailwind 4, but the move to Svelte 5 state runes/snippets and regressions checking will take some concentrated efforts and time. I don't know how close I'll try to sync their release schedules though (and the benefit of having |
|
All the examples give 500 errors on https://next.layerchart.com/ |
@cycle4passion Odd... working here
Maybe try a hard refresh? Which browser? |
|
mobile only, does not work in arc (chromium), native chrome, or Safari browser. |
Really odd... I can't reproduce
|
… support + unified `path` API
Narrow the layer toggle on an example page to the intersection of each used component's `layers` frontmatter, so e.g. a Chart example containing a Spline only exposes [svg, canvas] in the toggle. Affects 61 example toggles across the docs: 58 drop `html` (due ot path-geometry primitives such as Area, Spline, Arc, GeoPath, etc) and 3 drop`canvas` (due to Threshold/Blur).
…t` prop to render content *outside* the clip shape (cutouts/masks) across SVG, Canvas, and HTML layers
* Improve Tree controls * feat(Tree, Link, Connector): Add radial support * fix(canvas): Compose globalAlpha multiplicatively so Group opacity propagates to children * Rename "basic" example to "playground", improve playground, and add new basic * Show error message when an example fails to render * improve root node links for step curves * Improve tree playground example
* delay-screenshot-motion since adding lazy loaded charts which contain motion, screenshots for them are firing before they are rendered. I added "lazy-loaded" class to showControl.svelte, and check for that in generate-screenshots.ts. If found introduce pause to allow them to fully render. * delay-screenshot-motion since adding lazy loaded charts which contain motion, screenshots for them are firing before they are rendered. I added "screenshot-delay" class to showControl.svelte, and check for that in generate-screenshots.ts. If found introduce pause to allow them to fully render.
Currently <strong> text elements rendering dark Safari in darkmode. Webkit treats color: initial on inline replaced/formatted elements differently than Chrome/Firefox. The most reliable fix is avoiding inherit entirely and just setting an explicit color directly Example [Transform](https://next.layerchart.com/docs/guides/transform#pointer-interactions) Fix has been tested for dark and light modes in Safari, Chrome, Firefox.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…` node so snippet children (e.g. `<Rect fill={pattern}>`) render correctly
…ear-gradient` (lines) and `radial-gradient` (circles) values usable as a `background`/`fill`. Gradient-valued `background` (e.g. `<Pattern background={gradient}>`) is also supported.
…dth` to `1px` when `stroke` is set without an explicit `strokeWidth`, matching SVG's implicit `stroke-width: 1`. Also ensures Circle/Ellipse `border-width` gets the required `px` unit.
…`<Html>` layer by switching from `background-color` to the `background` shorthand (with `background-origin: border-box` to keep patterns aligned under the border). Accepts values produced by `<Pattern>` / `<LinearGradient>` in HTML mode.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…ted on band scales, and treat `null` on either side of `x`/`y` as "extend to chart edge".
…recedence over the computed series fade opacity. Regression introduced by per-segment styling refactor where the explicit `opacity` was spread after `series.props`, clobbering per-series opacity values (e.g. `series={[{ props: { opacity: 0.1 } }, ...]}`).
…le series when no series are configured. Restores grouped layout for composable `<Chart>` usage (e.g. `<Bars>` with `x1`/`x1Domain`/`x1Range`) where the visible-series filter previously emptied the secondary band scale domain, collapsing all bars to a single category position.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
7 participants
No description provided.